Skip to content

feat: add logging when publisherId is missing in VTEXAdsProvider#631

Closed
rogeralbinoi wants to merge 5 commits intomasterfrom
feat/publishedId-log
Closed

feat: add logging when publisherId is missing in VTEXAdsProvider#631
rogeralbinoi wants to merge 5 commits intomasterfrom
feat/publishedId-log

Conversation

@rogeralbinoi
Copy link
Copy Markdown

What problem is this solving?

This PR adds temporary logging functionality to track domains that don't have the publisherId configuration registered in the VTEXAdsProvider. This will help us quickly identify and fix domains missing this critical configuration.

Currently, when publisherId is missing, the component silently returns the children without any tracking mechanism. This makes it difficult to identify which domains need the configuration to be set up.

Note: This is a temporary solution for tracking purposes. Once we've identified and fixed all domains missing the configuration, this logging can be removed.

How to test it?

[Workspace](Link goes here!)

To test:

  1. Deploy this branch to a workspace
  2. Access a domain that doesn't have publisherId configured in the store settings
  3. Check the observability logs to verify that a log entry is created with the message "PublisherId não encontrado no VTEXAdsProvider"
  4. Verify that the component still renders correctly (returns children) even when the log is sent

@rogeralbinoi rogeralbinoi requested a review from a team as a code owner December 8, 2025 22:36
@rogeralbinoi rogeralbinoi requested review from RodrigoTadeuF, gabpaladino and vmourac-vtex and removed request for a team December 8, 2025 22:36
@vtex-io-ci-cd
Copy link
Copy Markdown
Contributor

vtex-io-ci-cd bot commented Dec 8, 2025

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@vtex-io-docs-bot
Copy link
Copy Markdown

vtex-io-docs-bot bot commented Dec 8, 2025

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

  • There's nothing new to document 🤔
  • I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

  • I just updated 🎉🎉

Copy link
Copy Markdown

@amandascm amandascm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👏🏼
(Se puder, adiciona aqui também as evidências que você testou e viu os logs chegarem)

@rogeralbinoi
Copy link
Copy Markdown
Author

After investigating a bit further, we identified that it won’t be possible to add these logs, because most stores without ADS would be triggered by the alerts. We have roughly 8k stores without ADS, which would result in a large number of false positives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants